Radio access control method, apparatus, and system

ABSTRACT

Embodiments of the present invention provide a radio access control method. The method includes that a terminal device receives access control information sent by an access network device, wherein the access control information indicates a barred service type and a barred data transmission attribute to the terminal device; and the terminal device determines whether to send a radio resource control (RRC) connection request to the access network device based on the barred service type and the barred data transmission attribute; wherein the data transmission attribute comprises a transmission scheme type, the transmission scheme type is used to indicate a transmission scheme used by the terminal device for transmitting service data used by the terminal device. Thereby improving network resource utilization.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/145,767, filed on Sep. 28, 2018, now U.S. Pat. No. 11,064,421. whichis a continuation of International Application No. PCT/CN2016/078181,filed on Mar. 31, 2016. All of the aforementioned patent applicationsare hereby incorporated by reference in their entireties.

TECHNICAL FIELD

Embodiments of the present invention relate to the communications field,and in particular, to a radio access control method, apparatus, andsystem.

BACKGROUND

A radio access technology (RAT) is a technology used when a terminaldevice accesses a mobile communications network. As communicationstechnologies and the Internet of Things (IoT) develop, the terminaldevice not only includes a first-type terminal device such as asmartphone and a tablet computer, but also includes a second-typeterminal device such as a smart meter and a smart instrument.

Generally, a radio access technology used by the first-type terminaldevice is referred to as wideband evolved Universal MobileTelecommunications System (UMTS) terrestrial radio access network(WB-E-UTRAN), and a radio access technology used by the second-typeterminal device is referred to as cellular-based Narrowband Internet ofThings (NB-IoT). Terminal devices use these two radio accesstechnologies to access a same base station and a same mobilitymanagement entity (MME). After a terminal device uses the WB-E-UTRAN toaccess a base station for a service, a user plane (UP) scheme is used totransmit service data. A data transmission path of the UP transmissionscheme is: terminal device→base station→serving gateway (SGW). After aterminal device uses the NB-IoT to access a base station for a service,a control plane (CP) scheme may be used to transmit service data inaddition to the UP scheme. A data transmission path of the CPtransmission scheme is: terminal device→base station→MME.

When load of the MME is relatively heavy, the MME sends an overloadstart (Overload Start) message to the base station. The overload startmessage instructs the base station to allow the terminal device toestablish RRC connections only for some types of services. However, fora type of service, when the UP scheme is used to transmit service data,the load of the MME is lighter; when the CP scheme is used to transmitservice data, the load of the MME is heavier. When the MME instructs thebase station to reject access of all services of a type, load impactcaused by different data transmission attributes of the terminal deviceis not considered, leading to relatively low MME resource utilization.

SUMMARY

Embodiments of the present invention provide a radio access controlmethod, apparatus, and system to resolve a problem of low MMEutilization caused because an MME whose load is relatively heavyinstructs a base station to reject access of all services of a type.

According to one embodiment, a radio access control method is provided,and the method includes: receiving, by a terminal device, access controlinformation sent by an access network device, where the access controlinformation indicates a barred service type and a barred datatransmission attribute and/or an allowed service type and an alloweddata transmission attribute to the terminal device; and determining, bythe terminal device based on the service type and the data transmissionattribute, whether to send a radio resource control (RRC) connectionrequest to the access network device, where the data transmissionattribute includes a transmission scheme type and/or a radio accesstechnology (RAT) type, the transmission scheme type indicates atransmission scheme used by the terminal device for transmitting servicedata, and the RAT type indicates a radio access technology used by theterminal device.

For this embodiment, an MME whose load is relatively heavy instructs tobar and/or allow access of some services meeting the data transmissionattribute in a type of service, instead of all services in this type ofservice. This resolves a problem of low MME resource utilization causedbecause the MME whose load is relatively heavy instructs the accessnetwork device to bar access of all services of a type, and achieves thefollowing effect: The access network device may bar and/or allow, basedon the instruction of the MME, only access of a service that meets boththe service type and the data transmission attribute, and servicecapabilities are provided for as many service types as possible withoutsignificantly increasing the load of the MME, thereby improving networkresource utilization.

For one embodiment, the access control information includes an accesscontrol factor and an access control time period; and the determining,based on the service type and the data transmission attribute, whetherto send an RRC connection request to the access network device includes:generating a random number when a service type of a current servicemeets the barred service type and a data transmission attributecorresponding to the current service meets the barred data transmissionattribute; determining whether the random number is less than the accesscontrol factor; and when the random number is less than the accesscontrol factor, determining to send the RRC connection request to theaccess network device; or when the random number is greater than orequal to the access control factor, setting a timer based on the accesscontrol time period, and when the timer expires, re-executing the stepof generating a random number.

For one embodiment, when the service type and the data transmissionattribute meet the barred service type and the barred data transmissionattribute, the terminal device generates the random number, compares therandom number with the access control factor, and then determineswhether to send the RRC connection request to the access network device,instead of directly giving up sending the RRC connection request. Theaccess network device allows random access of the terminal device,instead of directly rejecting access of the terminal device. Thisachieves the following effect: Service capabilities are provided for asmany service types as possible without significantly increasing the loadof the MME, thereby improving network resource utilization.

For one embodiment, the access control information includes an accessbarring class; and the determining, based on the service type and thedata transmission attribute, whether to send an RRC connection requestto the access network device includes: when a service type of a currentservice meets the barred service type and a data transmission attributecorresponding to the current service meets the barred data transmissionattribute, detecting whether an access class of the terminal device isequal to the access barring class, and if the access class of theterminal device is not equal to the access barring class, determining tosend the RRC connection request to the access network device; or when aservice type of a current service meets the barred service type and adata transmission attribute corresponding to the current service meetsthe barred data transmission attribute, detecting whether an accessclass of the terminal device is greater than the access barring class,and if the access class of the terminal device is less than the accessbarring class, determining to send the RRC connection request to theaccess network device; or when a service type of a current service meetsthe barred service type and a data transmission attribute correspondingto the current service meets the barred data transmission attribute,detecting whether an access class of the terminal device is less thanthe access barring class, and if the access class of the terminal deviceis greater than the access barring class, determining to send the RRCconnection request to the access network device.

For one embodiment, the access network device sends the access barringclass to the terminal device. The terminal device determines, based onthe access class of the terminal device and the access barring class,whether to send the RRC connection request. The terminal device sendsthe RRC connection request to the access network device for connectionand service transmission only when the access class of the terminaldevice is not equal to or is not greater than or is not less than theaccess barring class. This achieves the following effect: A service ispreferentially provided for a type of terminal device based on a servicetransmission requirement without significantly increasing the load ofthe MME.

For one embodiment, the determining, based on the service type and thedata transmission attribute, whether to send an RRC connection requestto the access network device includes: sending the RRC connectionrequest to the access network device when a service type of a currentservice meets the allowed service type and a data transmission attributecorresponding to the current service meets the allowed data transmissionattribute.

For one embodiment, the access control information includes a servicetype field and a data transmission attribute field, and the accesscontrol information has a default action type; or the access controlinformation includes an action type field, a service type field, and adata transmission attribute field.

For one embodiment, the action type field includes at least one ofaccess barred and access allowed; the service type field includes atleast one of an emergency service, a high-priority service, a mobileterminated service, a mobile originated signaling service, a mobileoriginated data service, a delay tolerant service, a mobile originatedvoice service, and a mobile originated exception service; and when thedata transmission attribute is the transmission scheme type, the datatransmission attribute field includes at least one of a user planescheme and a control plane scheme; or when the data transmissionattribute is the RAT type, the data transmission attribute fieldincludes at least one of the wideband evolved Universal MobileTelecommunications System (UMTS) terrestrial radio access network(WB-E-UTRAN) and the cellular-based Narrowband Internet of Things(NB-IoT).

According to one embodiment, a radio access control method is provided,and the method includes: receiving, by an access network device, anoverload start message sent by a mobility management entity (MME), wherethe overload start message indicates a barred service type and a barreddata transmission attribute and/or an allowed service type and anallowed data transmission attribute to the access network device;generating, by the access network device, access control informationbased on the overload start message, where the access controlinformation indicates the barred service type and the barred datatransmission attribute and/or the allowed service type and the alloweddata transmission attribute to a terminal device; and sending, by theaccess network device, the access control information to the terminaldevice, where the data transmission attribute includes a transmissionscheme type and/or a RAT type, the transmission scheme type indicates atransmission scheme used by the terminal device for transmitting servicedata, and the RAT type indicates a radio access technology used by theterminal device.

In the embodiment, the MME whose load is relatively heavy instructs tobar and/or allow access of some services meeting the data transmissionattribute in a type of service, instead of all services in this type ofservice. This resolves a problem of low MME resource utilization causedbecause the MME whose load is relatively heavy instructs the accessnetwork device to bar access of all services of a type, and achieves thefollowing effect: The access network device may bar and/or allow, basedon the instruction of the MME, only access of a service that meets boththe service type and the data transmission attribute, and servicecapabilities are provided for as many service types as possible withoutsignificantly increasing the load of the MME, thereby improving networkresource utilization.

For one embodiment, the access control information includes an accesscontrol factor and an access control time period.

For one embodiment, the access control information includes an accessbarring class.

For one embodiment, the overload start message includes a service typefield and a data transmission attribute field, and the overload startmessage has a default action type; or the overload start messageincludes an action type field, a service type field, and a datatransmission attribute field.

For one embodiment, the action type field includes at least one ofaccess barred and access allowed; the service type field includes atleast one of an emergency service, a high-priority service, a mobileterminated service, a mobile originated signaling service, a mobileoriginated data service, a delay tolerant service, a mobile originatedvoice service, and a mobile originated exception service; and when thedata transmission attribute is the transmission scheme type, the datatransmission attribute field includes at least one of a user planescheme and a control plane scheme; or when the data transmissionattribute is the RAT type, the data transmission attribute fieldincludes at least one of the WB-E-UTRAN and the NB-IoT.

According to one embodiment, a radio access control method is provided,and the method includes: sending, by a terminal device, an RRCconnection request message to an access network device, where the RRCconnection request has a corresponding service type and a correspondingdata transmission attribute; and receiving, by the terminal device, anRRC connection setup message or an RRC connection reject message sent bythe access network device, where the RRC connection setup message or theRRC connection reject message is sent by the access network device basedon whether the service type and the data transmission attribute that arecorresponding to the RRC connection request belong to a barred servicetype and a barred data transmission attribute and/or an allowed servicetype and an allowed data transmission attribute, where the datatransmission attribute includes a transmission scheme type and/or a RATtype, the transmission scheme type indicates a transmission scheme usedby the terminal device for transmitting service data, and the RAT typeindicates a radio access technology used by the terminal device.

In the embodiment, an MME whose load is relatively heavy instructs tobar and/or allow access of some services meeting the data transmissionattribute in a type of service, instead of all services in this type ofservice. This resolves a problem of low MME resource utilization causedbecause the MME whose load is relatively heavy instructs the accessnetwork device to bar access of all services of a type, and achieves thefollowing effect: The access network device may bar and/or allow, basedon the instruction of the MME, only access of a service that meets boththe service type and the data transmission attribute, and servicecapabilities are provided for as many service types as possible withoutsignificantly increasing the load of the MME, thereby improving networkresource utilization.

For one embodiment, the RRC connection request message includes aservice type field and a data transmission attribute field.

For one embodiment, the service type field includes at least one of anemergency service, a high-priority service, a mobile terminated service,a mobile originated signaling service, a mobile originated data service,a delay tolerant service, a mobile originated voice service, and amobile originated exception service; and when the data transmissionattribute is the transmission scheme type, the data transmissionattribute field includes at least one of a user plane scheme and acontrol plane scheme; or when the data transmission attribute is the RATtype, the data transmission attribute field includes at least one of theWB-E-UTRAN and the NB-IoT.

For one embodiment, the method further includes: sending, by theterminal device, the data transmission attribute corresponding to theRRC connection request to the access network device, where the RRCconnection request message includes a service type field.

According to one embodiment, a radio access control method is provided,and the method includes: receiving, by an access network device, anoverload start message sent by an MME, where the overload start messageindicates a barred service type and a barred data transmission attributeand/or an allowed service type and an allowed data transmissionattribute to the access network device; receiving, by the access networkdevice, an RRC connection request message sent by a terminal device,where the RRC connection request has a corresponding service type and acorresponding data transmission attribute; and sending, by the accessnetwork device, an RRC connection setup message or an RRC connectionreject message to the terminal device based on whether the service typeand the data transmission attribute that are corresponding to the RRCconnection request belong to the barred service type and the barred datatransmission attribute and/or the allowed service type and the alloweddata transmission attribute, where the data transmission attributeincludes a transmission scheme type and/or a RAT type, the transmissionscheme type indicates a transmission scheme used by the terminal devicefor transmitting service data, and the RAT type indicates a radio accesstechnology used by the terminal device.

In the embodiment, the MME whose load is relatively heavy instructs tobar and/or allow access of some services meeting the data transmissionattribute in a type of service, instead of all services in this type ofservice. This resolves a problem of low MME resource utilization causedbecause the MME whose load is relatively heavy instructs the accessnetwork device to bar access of all services of a type, and achieves thefollowing effect: The access network device may bar and/or allow, basedon the instruction of the MME, only access of a service that meets boththe service type and the data transmission attribute, and servicecapabilities are provided for as many service types as possible withoutsignificantly increasing the load of the MME, thereby improving networkresource utilization.

For one embodiment, the RRC connection request message includes aservice type field and a data transmission attribute field.

For one embodiment, the service type field includes at least one of anemergency service, a high-priority service, a mobile terminated service,a mobile originated signaling service, a mobile originated data service,a delay tolerant service, a mobile originated voice service, and amobile originated exception service; and when the data transmissionattribute is the transmission scheme type, the data transmissionattribute field includes at least one of a user plane scheme and acontrol plane scheme; or when the data transmission attribute is the RATtype, the data transmission attribute field includes at least one of theWB-E-UTRAN and the NB-IoT.

For one embodiment, the method further includes: receiving, by theaccess network device, the data transmission attribute that iscorresponding to the RRC connection request and that is sent by theterminal device, where the RRC connection request message includes aservice type field.

For one embodiment, the sending, by the access network device, an RRCconnection setup message or an RRC connection reject message to theterminal device based on whether the service type and the datatransmission attribute that are corresponding to the RRC connectionrequest belong to the barred service type and the barred datatransmission attribute and/or the allowed service type and the alloweddata transmission attribute includes: sending the RRC connection setupmessage to the terminal device when the service type and the datatransmission attribute that are corresponding to the RRC connectionrequest are the allowed service type and the allowed data transmissionattribute; or sending the RRC connection reject message to the terminaldevice when the service type and the data transmission attribute thatare corresponding to the RRC connection request are the barred servicetype and the barred data transmission attribute.

According to one embodiment, a radio access control method is provided,and the method includes: sending, by an MME, an overload start messageto an access network device when load is greater than a presetcondition, where the overload start message indicates a barred servicetype and a barred data transmission attribute and/or an allowed servicetype and an allowed data transmission attribute to the access networkdevice, the data transmission attribute includes a transmission schemetype and/or a RAT type, the transmission scheme type indicates atransmission scheme used by a terminal device for transmitting servicedata, and the RAT type indicates a radio access technology used by theterminal device.

In the embodiment, the MME whose load is relatively heavy instructs tobar and/or allow access of some services meeting the data transmissionattribute in a type of service, instead of all services in this type ofservice. This resolves a problem of low MME resource utilization causedbecause the MME whose load is relatively heavy instructs the accessnetwork device to bar access of all services of a type, and achieves thefollowing effect: The access network device may bar and/or allow, basedon the instruction of the MME, only access of a service that meets boththe service type and the data transmission attribute, and servicecapabilities are provided for as many service types as possible withoutsignificantly increasing the load of the MME, thereby improving networkresource utilization.

For one embodiment, the overload start message includes a service typefield and a data transmission attribute field, and the overload startmessage has a default action type; or the overload start messageincludes an action type field, a service type field, and a datatransmission attribute field.

For one embodiment, the action type field includes at least one ofaccess barred and access allowed; the service type field includes atleast one of an emergency service, a high-priority service, a mobileterminated service, a mobile originated signaling service, a mobileoriginated data service, a delay tolerant service, a mobile originatedvoice service, and a mobile originated exception service; and when thedata transmission attribute is the transmission scheme type, the datatransmission attribute field includes at least one of a user planescheme and a control plane scheme; or when the data transmissionattribute is the RAT type, the data transmission attribute fieldincludes at least one of the WB-E-UTRAN and the NB-IoT.

According to one embodiment, a terminal device is provided. The terminaldevice has a function of implementing behavior of the terminal device inthe radio access control method according to the first aspect and/or thethird aspect. The function may be implemented by hardware, or may beimplemented by hardware executing corresponding software. The hardwareor the software includes one or more modules corresponding to thefunction.

For one embodiment, a structure of the terminal device includes aprocessor, a transmitter, and a receiver. The processor is configured tosupport the terminal device in executing a corresponding function in theforegoing method. The transmitter and the receiver are configured to:support communication between the terminal device and an access networkdevice, send information or an instruction in the foregoing method tothe access network device, and receive information or an instruction inthe foregoing method that is sent by the access network device. Theterminal device may further include a memory. The memory is configuredto be coupled with the processor, and store a necessary programinstruction and necessary data of the terminal device.

According to one embodiment, an access network device is provided. Theaccess network device has a function of implementing behavior of theaccess network device in the radio access control method according tothe second aspect and/or the fourth aspect. The function may beimplemented by hardware, or may be implemented by hardware executingcorresponding software. The hardware or the software includes one ormore modules corresponding to the function.

For one embodiment, a structure of the access network device includes aprocessor, a transmitter, and a receiver. The processor is configured tosupport the access network device in executing a corresponding functionin the foregoing method. The transmitter and the receiver are configuredto: support communication between the access network device and aterminal device and/or an MME, send information or an instruction in theforegoing method to the terminal device and/or the MME, and receiveinformation or an instruction in the foregoing method that is sent bythe terminal device and/or the MME. The access network device mayfurther include a memory. The memory is configured to be coupled withthe processor, and store a necessary program instruction and necessarydata of the access network device.

According to one embodiment, an MME is provided. The MME has a functionof implementing behavior of the MME in the radio access control methodaccording to the third aspect. The function may be implemented byhardware, or may be implemented by hardware executing correspondingsoftware. The hardware or the software includes one or more modulescorresponding to the function.

For one embodiment, a structure of the MME includes a processor, atransmitter, and a receiver. The processor is configured to support theMME in executing a corresponding function in the foregoing method. Thetransmitter and the receiver are configured to: support communicationbetween the MME and an access network device, send information or aninstruction in the foregoing method to the access network device, andreceive information or an instruction in the foregoing method that issent by the access network device. The MME may further include a memory.The memory is configured to be coupled with the processor, and store anecessary program instruction and necessary data of the MME.

According to one embodiment, a radio access control system is provided.The radio access control system includes the terminal device accordingto the sixth aspect, the access network device according to the seventhaspect, and the MME according to the eighth aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic structural diagram of a radio access controlsystem according to an example embodiment of the present invention;

FIG. 2 is a schematic diagram of service transmission according to anexample embodiment of the present invention;

FIG. 3 is a schematic diagram of service transmission according to anexample embodiment of the present invention;

FIG. 4 is a flowchart of a radio access control method according to anexample embodiment of the present invention;

FIG. 5A and FIG. 5B are a flowchart of a radio access control methodaccording to an example embodiment of the present invention;

FIG. 6A and FIG. 6B are a flowchart of a radio access control methodaccording to another example embodiment of the present invention;

FIG. 7 is a flowchart of a radio access control method according toanother example embodiment of the present invention;

FIG. 8A and FIG. 8B are a flowchart of a radio access control methodaccording to another example embodiment of the present invention;

FIG. 9 is a flowchart of a radio access control method according toanother example embodiment of the present invention;

FIG. 10A and FIG. 10B are a flowchart of a radio access control methodaccording to another example embodiment of the present invention;

FIG. 11 is a flowchart of a radio access control method according toanother example embodiment of the present invention;

FIG. 12A is a flowchart of a radio access control method according toanother example embodiment of the present invention;

FIG. 12B is a flowchart of a radio access control method according toanother example embodiment of the present invention;

FIG. 13A is a block diagram of a radio access control apparatusaccording to an example embodiment of the present invention;

FIG. 13B is a block diagram of a radio access control apparatusaccording to an example embodiment of the present invention;

FIG. 14 is a block diagram of a radio access control apparatus accordingto another example embodiment of the present invention; and

FIG. 15 is a block diagram of a radio access control apparatus accordingto another example embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

A “module” mentioned in this specification is a program or aninstruction that is stored in a memory and may implement some functions.A “unit” mentioned in this specification is a functional structuredivided based on logic. The “unit” may be implemented by only hardware,or implemented by a combination of software and hardware.

In this specification, “a plurality of” refers to two or more than two.The term “and/or” describes an association relationship for describingassociated objects and represents that three relationships may exist.For example, A and/or B may represent the following three cases: Only Aexists, both A and B exist, and only B exists. The character “I” usuallyindicates an “or” relationship between the associated objects.

Referring to FIG. 1 , FIG. 1 is a schematic structural diagram of aradio access control system according to an example embodiment of thepresent invention. The radio access control system includes a terminaldevice 120, an access network device 140, a mobility management entity(MME) 160, and a serving gateway (SGW) 180.

The terminal device 120 may be a first-type terminal device or asecond-type terminal device. The first-type terminal device is anelectronic device having a radio communication capability, such as asmartphone, a tablet computer, an e-book reader, and a portablecomputer. The second-type terminal device may be a smart instrument or asmart meter having a radio communication capability.

The terminal device 120 may use a radio access technology (RAT) toaccess a mobile communications network provided by the access networkdevice 140. RAT types include but are not limited to wideband evolvedUniversal Mobile Telecommunications System (UMTS) terrestrial radioaccess network (WB-E-UTRAN), cellular-based Narrowband Internet ofThings (NB-IoT), and the 5th generation mobile communications technology(5G).

When the terminal device 120 is a first-type terminal device, a RAT typeused by the terminal device 120 may be the WB-E-UTRAN. An availablefrequency band of the WB-E-UTRAN is wider.

When the terminal device 120 is a second-type terminal device, a RATtype used by the terminal device 120 may be the NB-IoT. An availablefrequency band of the NB-IoT is narrower.

The access network device 140 is a network element interacting with theterminal device 120, and the access network device 130 may be a basestation.

Optionally, the access network device 140 is a base station (BTS) inGlobal System for Mobile Communications (GSM) or Code Division MultipleAccess (CDMA).

Optionally, the access network device 140 is a base station (NodeB) inUMTS.

Optionally, the access network device 140 is an evolved NodeB (eNB ore-NodeB) in Long Term Evolution (Long Term Evolution, LTE).

Optionally, the access network device 140 is an access point (AP) inWireless Fidelity (WI-FI).

The MME 160 is a network element corresponding to a control plane CP) inthe radio access control system. The SGW 180 is a network elementcorresponding to a user plane (UP) in the radio access control system.The access network device 140 is separately connected to the MME 160 andthe SGW 180 by using a wireless network or a wired network. The MME 160is connected to the SGW 180 by using a wireless network or a wirednetwork.

It should be noted that the radio access control system may include aplurality of terminal devices 120 and a plurality of access networkdevices 140. One access network device 140 may communicate with aplurality of terminal devices 120, and the plurality of terminal devices120 that communicate with the access network device 140 may befirst-type terminal devices or second-type terminal devices. In FIG. 1 ,only one terminal device 120 and one access network device 140 are shownfor example description.

When the terminal device 120 is a first-type terminal device, and aservice transmitted by the terminal device 120 is at least one of anemergency service (emergency), a high-priority service(highPriorityAccess), a mobile terminated service (mt-Access), a mobileoriginated signaling service (mo-Signaling), a mobile originated dataservice (mo-Data), a delay tolerant service (delayTolerantAccess), and amobile originated voice service (mo-VoiceCall), the terminal device 120uses the WB-E-UTRAN to send a radio resource control (Radio ResourceControl, RRC) connection request to the access network device 140, torequest to establish an RRC connection with the access network device140. After establishing the RRC connection with the access networkdevice 140, the terminal device 120 establishes communication with theMME 160 by using the access network device 140, so that the terminaldevice 120 accesses the mobile communications network.

After establishing the RRC connection with the access network device140, the terminal device 120 uses the WB-E-UTRAN to transmit theservice. A transmission scheme used by the terminal device 120 fortransmitting the service is a user plane scheme: The first-type terminaldevice uses a data radio bearer (Data Radio Bearer, DRB) in the RRCconnection to send service data of the service to the access networkdevice 140, and then the access network device 140 sends the servicedata of the service to the SGW 180 to implement service transmission.When the terminal device 120 is a first-type terminal device, aschematic transmission diagram in which the terminal device 120transmits the service is shown in FIG. 2 .

When the terminal device 120 is a second-type terminal device, and aservice transmitted by the terminal device 120 is at least one of amobile terminated service, a mobile originated signaling service, amobile originated data service, and a mobile originated exceptionservice (mo-ExceptionData), the terminal device 120 uses the NB-IoT tosend an RRC connection request to the access network device 140, torequest to establish an RRC connection with the access network device140. After establishing the RRC connection with the access networkdevice 140, the terminal device 120 establishes communication with theMME 160 by using the access network device 140, so that the terminaldevice 120 accesses the mobile communications network.

After establishing the RRC connection with the access network device140, the terminal device 120 uses the NB-IoT to transmit the service. Atransmission scheme used by the terminal device 120 for transmitting theservice is a user plane scheme or a control plane scheme. When theterminal device 120 uses the user plane scheme to transmit the service,the terminal device 120 uses a DRB to send service data of the serviceto the access network device 140, and then the access network device 140sends the service data of the service to the SGW 180 to implementservice transmission. When the terminal device 120 uses the controlplane scheme to transmit the service, the terminal device 120 uses asignaling radio bearer (SRB) to send service data of the service to theaccess network device 140, and then the access network device 140 sendsthe service data of the service to the MME 160 to implement servicetransmission. When the terminal device 120 is a second-type terminaldevice, a schematic transmission diagram in which the terminal device120 transmits the service is shown in FIG. 3 .

Referring to FIG. 4 , FIG. 4 is a flowchart of a radio access controlmethod according to an example embodiment of the present invention. Thisembodiment is described by using an example in which the method isapplied to the radio access control system shown in FIG. 1 . The methodincludes the following steps.

Step 401: An MME sends an overload start (Overload Start) message to anaccess network device when load is greater than a preset condition,where the overload start message indicates a barred service type and abarred data transmission attribute and/or an allowed service type and anallowed data transmission attribute to the access network device.

The data transmission attribute includes a transmission scheme typeand/or a RAT type. The transmission scheme type indicates a transmissionscheme used by a terminal device for transmitting service data. The RATtype indicates a radio access technology used by the terminal device.

Step 402: The access network device receives the overload start messagesent by the MME.

Step 403: The access network device generates access control informationbased on the overload start message, where the access controlinformation indicates the barred service type and the barred datatransmission attribute and/or the allowed service type and the alloweddata transmission attribute to a terminal device.

Step 404: The access network device sends the access control informationto the terminal device.

Step 405: The terminal device receives the access control informationsent by the access network device.

Step 406: The terminal device determines, based on the service type andthe data transmission attribute, whether to send an RRC connectionrequest to the access network device.

Step 401 may be independently implemented as a radio access controlmethod on an MME side. Step 402, step 403, and step 404 may beindependently implemented as a radio access control method on an accessnetwork device side. Step 405 and step 406 may be independentlyimplemented as a radio access control method on a terminal device side.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME whose load isrelatively heavy instructs to bar and/or allow access of some servicesmeeting the data transmission attribute in a type of service, instead ofall services in this type of service. This resolves a problem of low MMEresource utilization caused because the MME whose load is relativelyheavy instructs the access network device to bar access of all servicesof a type, and achieves the following effect: The access network devicemay bar and/or allow, based on the instruction of the MME, only accessof a service that meets both the service type and the data transmissionattribute, and service capabilities are provided for as many servicetypes as possible without significantly increasing the load of the MME,thereby improving network resource utilization.

Referring to FIG. 5A and FIG. 5B, FIG. 5A and FIG. 5B are a flowchart ofa radio access control method according to another example embodiment ofthe present invention. This embodiment is described by using an examplein which the method is applied to the radio access control system shownin FIG. 1 . The method includes the following steps.

Step 501: An MME sends an overload start message to an access networkdevice when load is greater than a preset condition, where the overloadstart message indicates a barred service type and a barred datatransmission attribute and/or an allowed service type and an alloweddata transmission attribute to the access network device.

The data transmission attribute includes a transmission scheme typeand/or a RAT type. The transmission scheme type indicates a transmissionscheme used by a terminal device for transmitting service data. The RATtype indicates a radio access technology used by the terminal device.

Step 502: The access network device receives the overload start messagesent by the MME.

Step 503: A terminal device sends an RRC connection request message tothe access network device, where the RRC connection request has acorresponding service type and a corresponding data transmissionattribute.

Step 504: The access network device receives the RRC connection requestmessage sent by the terminal device.

Step 505: The access network device sends an RRC connection setupmessage or an RRC connection reject message to the terminal device basedon whether the service type and the data transmission attribute that arecorresponding to the RRC connection request belong to the barred servicetype and the barred data transmission attribute and/or the allowedservice type and the allowed data transmission attribute.

Step 506: The terminal device receives the RRC connection setup messageor the RRC connection reject message sent by the access network device.

Step 501 may be independently implemented as a radio access controlmethod on an MME side. Step 502, step 504, and step 505 may beindependently implemented as a radio access control method on an accessnetwork device side. Step 503 and step 506 may be independentlyimplemented as a radio access control method on a terminal device side.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME whose load isrelatively heavy instructs to bar and/or allow access of some servicesmeeting the data transmission attribute in a type of service, instead ofall services in this type of service. This resolves a problem of low MMEresource utilization caused because the MME whose load is relativelyheavy instructs the access network device to bar access of all servicesof a type, and achieves the following effect: The access network devicemay bar and/or allow, based on the instruction of the MME, only accessof a service that meets both the service type and the data transmissionattribute, and service capabilities are provided for as many servicetypes as possible without significantly increasing the load of the MME,thereby improving network resource utilization.

A data transmission attribute includes a transmission scheme type and/ora RAT type. The following embodiment is described by using an example inwhich the data transmission attribute is the transmission scheme type.In this case, a data transmission attribute field is a transmissionscheme type field.

Referring to FIG. 6A and FIG. 6B, FIG. 6A and FIG. 6B are a flowchart ofa radio access control method according to an example embodiment of thepresent invention. This embodiment is described by using an example inwhich the method is applied to the radio access control system shown inFIG. 1 . The method includes the following steps.

Step 601: An MME sends an overload start message to an access networkdevice when load is greater than a preset condition, where the overloadstart message indicates a barred service type and a barred transmissionscheme type and/or an allowed service type and an allowed transmissionscheme type to the access network device.

Two different implementations are available for the MME to send theoverload start message to the access network device to indicate thebarred service type and the barred transmission scheme type and/or theallowed service type and the allowed transmission scheme type. Theoverload start message includes different content in differentimplementations.

In a first possible implementation, the overload start message includesa service type field and a transmission scheme type field. The overloadstart message has a default action type. The action type is accessbarred or access allowed. Optionally, the default action type of theoverload start message is preset.

For example, the default action type of the overload start message isaccess barred, and information carried in the overload start message is(mo-Data, CP), where mo-Data is the service type field, and CP is thetransmission scheme type field. The overload start message indicatesthat a mo-Data service transmitted by using a CP scheme is barred.

In a second possible implementation, the overload start message includesan action type field, a service type field, and a transmission schemetype field. The action type field indicates an action type of theoverload start message, and the action type field includes at least oneof access barred and access allowed.

For example, information carried in the overload start message is(allowed, mo-Data, UP), where allowed is the action type field, mo-Datais the service type field, and UP is the transmission scheme type field.The overload start message indicates that a mo-Data service transmittedby using a UP scheme is allowed.

A form and content of the overload start message are not limited in thisembodiment.

In the two possible implementations, the service type field indicates aservice type, and the service type field includes at least one of anemergency service, a high-priority service, a mobile terminated service,a mobile originated signaling service, a mobile originated data service,a delay tolerant service, a mobile originated voice service, and amobile originated exception service.

The transmission scheme type field indicates a transmission scheme usedfor a service, and the transmission scheme type field includes at leastone of a user plane scheme and a control plane scheme.

Optionally, the “preset condition” in that the load is greater than thepreset condition is a preset value in the system or a condition definedby operation and maintenance personnel, and this is not limited in thisembodiment.

Optionally, when the MME needs to indicate a plurality of action typesand/or service types and/or transmission scheme types to the accessnetwork device, the MME may perform centralized indication in oneoverload start message sent to the access network device, or performseparate indication in a plurality of overload start messages sent tothe access network device. This is not limited in this embodiment.

For example, when the MME needs to indicate, to the access networkdevice, that a mo-Data service transmitted by using the CP scheme isbarred, and that a mo-ExceptionData service transmitted by using the CPscheme is barred, the MME may perform centralized indication in a sameoverload start message, for example ((mo-Data, CP), (mo-ExceptionData,CP)), and the default action type of the overload start message isaccess barred. Alternatively, the MME may perform separate indication ina plurality of overload start messages. One overload start message is(barred, mo-Data, CP), and the other overload start message is (barred,mo-ExceptionData, CP).

Step 602: The access network device receives the overload start messagesent by the MME.

When the overload start message includes the service type field and thetransmission scheme type field, and the overload start message has thedefault action type, the access network device determines the defaultaction type of the overload start message, obtains a service type byparsing the service type field, and obtains a transmission scheme typeby parsing the transmission scheme type field.

When the overload start message includes the action type field, theservice type field, and the transmission scheme type field, the accessnetwork device obtains an action type by parsing the action type field,obtains a service type by parsing the service type field, and obtains atransmission scheme type by parsing the transmission scheme type field.

Step 603: The access network device generates access control informationbased on the overload start message, where the access controlinformation indicates the barred service type and the barred datatransmission attribute and/or the allowed service type and the allowedtransmission scheme type to a terminal device.

An action type indicated by the access control information is the sameas the action type that is of the overload start message and that isdetermined by the access network device.

A service type indicated by the access control information is the sameas the service type obtained by the access network device by parsing theservice type field in the overload start message. A transmission schemetype indicated by the access control information is the same as thetransmission scheme type obtained by the access network device byparsing the data transmission attribute field in the overload startmessage.

Two different implementations are available for the access networkdevice to indicate the barred service type and the barred transmissionscheme type and/or the allowed service type and the allowed transmissionscheme type to the terminal device by using the generated access controlinformation. The access control information includes different contentin different implementations.

In a first possible implementation, the access control informationincludes a service type field and a data transmission attribute field.The access control information has a default action type. The actiontype is at least one of access barred and access allowed.

In a second possible implementation, the access control informationincludes an action type field, a service type field, and a datatransmission attribute field. The action type field indicates an actiontype of the access control information, and the action type fieldincludes at least one of access barred and access allowed.

An implementation used in this step is not limited in this embodiment.

A form of the access control information may be the same as the form ofthe overload start message. Details are not described again in thisembodiment.

Step 604: The access network device sends the access control informationto the terminal device.

Optionally, the access network device uses dedicated signaling to sendthe access control information to the terminal device, or sends theaccess control information in a broadcast message form in coverage ofthe access network device.

When the access network device needs to indicate a plurality of actiontypes and/or service types and/or transmission scheme types to theterminal device, the access network device performs centralizedindication in one piece of access control information sent to theterminal device, or performs separate indication in a plurality ofpieces of access control information sent to the terminal device. Thisis not limited in this embodiment.

Step 605: The terminal device receives the access control informationsent by the access network device.

When the access control information includes the service type field andthe data transmission attribute field, and the access controlinformation has the default action type, the terminal device determinesthe default action type of the access control information, obtains aservice type by parsing the service type field, and obtains atransmission scheme type by parsing the data transmission attributefield.

When the access control information includes the action type field, theservice type field, and the data transmission attribute field, theterminal device obtains an action type by parsing the action type field,obtains a service type by parsing the service type field, and obtains atransmission scheme type by parsing the data transmission attributefield.

The action type is at least one of access barred and access allowed.When the action type is access allowed, the method includes thefollowing step 606:

Step 606: The terminal device sends an RRC connection request to theaccess network device when a service type of a current service meets theallowed service type and a transmission scheme type corresponding to thecurrent service meets the allowed transmission scheme type.

The transmission scheme type corresponding to the current service is atransmission scheme type used by the terminal device for transmittingthe current service.

The service type obtained by the terminal device by parsing the servicetype field in the access control information is an allowed service. Thetransmission scheme type obtained by parsing the data transmissionattribute field is the allowed transmission scheme type.

For example, if the access control information received by the terminaldevice is (mo-Data, UP), and the default action type of the accesscontrol information is access allowed, the terminal device determines,by parsing the access control information, that the access controlinformation indicates that an allowed service is a mo-Data servicetransmitted by using the UP scheme. When a service currently to betransmitted by the terminal device is a mo-Data service transmitted byusing the UP scheme, the terminal device sends the RRC connectionrequest to the access network device. When the service currently to betransmitted by the terminal device is a mo-Data service transmitted byusing the CP scheme, the terminal device does not send the RRCconnection request to the access network device.

Two different implementations are available when the action type isaccess barred.

In a first implementation, the access control information received bythe terminal device includes an access control factor and an accesscontrol time period. The terminal device determines, based on the accesscontrol factor and the access control time period, whether to send anRRC connection request to the access network device.

The access control factor is a threshold used to be compared with arandom number generated by the terminal device. The access control timeperiod is used to set a time period for a timer when the random numbergenerated by the terminal device is greater than or equal to the accesscontrol factor.

In a second implementation, the access control information received bythe terminal device includes an access barring class. The terminaldevice determines, based on the access barring class, whether to send anRRC connection request to the access network device.

In this embodiment, if the first implementation is used as an examplefor description, the method further includes the following step 607 tostep 610.

Step 607: Generate a random number when a service type of a currentservice meets the barred service type and a transmission scheme typecorresponding to the current service meets the barred transmissionscheme type.

The terminal device generates, according to a predetermined algorithm, arandom number falling within (0, 1).

Step 608: The terminal device determines whether the random number isless than an access control factor.

Optionally, the access control factor is equal to 0.5.

Step 609: When the random number is less than the access control factor,the terminal device determines to send an RRC connection request to theaccess network device.

Step 610: When the random number is greater than or equal to the accesscontrol factor, set a timer based on an access control time period, andwhen the timer expires, re-execute the step of generating a randomnumber.

Optionally, the access control time period is 10 seconds.

Optionally, timing duration of the timer=(0.7+0.6×rand)×access controltime period, where rand is a random number that is generated by theterminal device and that is evenly distributed between 0 and 1. When thetimer expires, step 607 is re-executed. It should be noted that step 609and step 610 may be alternatively implemented as follows: When therandom number is greater than or equal to the access control factor, theterminal device determines to send an RRC connection request to theaccess network device; when the random number is less than the accesscontrol factor, set a timer based on an access control time period, andwhen the timer expires, re-execute the step of generating a randomnumber. This is not limited in this embodiment.

In an example, the access control information received by the terminaldevice is (barred, mo-Data, CP). The terminal device determines, byparsing the access control information, that the access controlinformation indicates that a barred service is a mo-Data servicetransmitted by using the CP scheme. When a service type of a servicecurrently transmitted by the terminal device is a mo-Data service, and atransmission scheme type used by the terminal device for transmittingthe service is the CP scheme, the terminal device determines, based onthe access control information, that the access control factor is 0.5and the access control time period is 10 seconds. If the terminal devicegenerates a random number such as 0.7, because 0.7>0.5, the terminaldevice generates another random number such as 0.4. In this case, theterminal device sets the timing duration of the timer to(0.7+0.6×0.4)×10=9.4 seconds. When the timer expires, that is, after 9.4seconds, the terminal device generates another random number such as0.3. Because 0.3<0.5, the terminal device determines to send the RRCconnection request to the access network device.

It should be noted that one piece of access control information mayindicate a plurality of action types, and the action types may includeboth access allowed and access barred. However, no intersection existsbetween a service type and a transmission scheme type for which accessis allowed and a service type and a transmission scheme type for whichaccess is barred. A related implementation is the same as that in theforegoing method. Details are not described again in this embodiment.

An optional embodiment based on the foregoing embodiment is described byusing an example in which the action type of the access controlinformation received by the terminal device is access barred, and thesecond implementation is used to determine whether to send the RRCconnection request to the access network device. In this case, theaccess control information received by the terminal device furtherincludes the access barring class, and step 607 to step 610 may bealternatively implemented as any one of the following steps, as shown inFIG. 7 .

Step 701: When a service type of a current service meets the barredservice type and a transmission scheme type corresponding to the currentservice meets the barred transmission scheme type, detect whether anaccess class of the terminal device is equal to an access barring class;and if the access class of the terminal device is not equal to theaccess barring class, the terminal device determines to send an RRCconnection request to the access network device.

Different terminal devices have different access classes. The accessclass of the terminal device is preset.

In an example, the access control information received by the terminaldevice is (barred, mo-Data, CP). The terminal device determines, byparsing the access control information, that the access controlinformation indicates that a barred service is a mo-Data servicetransmitted by using the CP scheme. When a service type of a servicecurrently transmitted by the terminal device is a mo-Data service, and atransmission scheme type used by the terminal device for transmittingthe service is the CP scheme, the terminal device determines that theaccess barring class included in the access control information is 2.When the access class of the terminal device is 2, the terminal devicedoes not send the RRC connection request to the access network device.When the access class of the terminal device is 3, the terminal devicesends the RRC connection request to the access network device.

Alternatively, another alternative implementation solution of step 701is illustrated in step 702.

Step 702: When a service type of a current service meets the barredservice type and a transmission scheme type corresponding to the currentservice meets the barred transmission scheme type, detect whether anaccess class of the terminal device is greater than an access barringclass; and if the access class of the terminal device is less than theaccess barring class, determine to send an RRC connection request to theaccess network device.

In the foregoing example embodiment, when the service type of theservice currently transmitted by the terminal device is a mo-Dataservice, and the transmission scheme type used by the terminal devicefor transmitting the service is the CP scheme, the terminal devicedetermines that the access barring class included in the access controlinformation is 2. If the access class of the terminal device is 1, theterminal device sends the RRC connection request to the access networkdevice. If the access class of the terminal device is 3, the terminaldevice does not send the RRC connection request to the access networkdevice.

Alternatively, another alternative implementation solution of step 701is illustrated in step 703.

Step 703: When a service type of a current service meets the barredservice type and a transmission scheme type corresponding to the currentservice meets the barred transmission scheme type, detect whether anaccess class of the terminal device is less than an access barringclass; and if the access class of the terminal device is greater thanthe access barring class, determine to send an RRC connection request tothe access network device.

In the foregoing example embodiment, when the service type of theservice currently transmitted by the terminal device is a mo-Dataservice, and the transmission scheme type used by the terminal devicefor transmitting the service is the CP scheme, the terminal devicedetermines that the access barring class included in the access controlinformation is 2. If the access class of the terminal device is 3, theterminal device sends the RRC connection request to the access networkdevice. If the access class of the terminal device is 1, the terminaldevice does not send the RRC connection request to the access networkdevice.

In this embodiment, the terminal device executes any one of step 701 tostep 703. A specific used step is not limited in this embodiment.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME whose load isrelatively heavy instructs to bar and/or allow access of some servicesmeeting the data transmission attribute in a type of service, instead ofall services in this type of service. This resolves a problem of low MMEresource utilization caused because the MME whose load is relativelyheavy instructs the access network device to bar access of all servicesof a type, and achieves the following effect: The access network devicemay bar and/or allow, based on the instruction of the MME, only accessof a service that meets both the service type and the data transmissionattribute, and service capabilities are provided for as many servicetypes as possible without significantly increasing the load of the MME,thereby improving network resource utilization.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME indicates thebarred service type and the barred transmission scheme type and/or theallowed service type and the allowed transmission scheme type to theaccess network device. In this way, the MME may instruct the accessnetwork device to bar and/or allow access of a service transmitted byusing a transmission scheme type. Because load of the MME when servicedata is transmitted by using the user plane scheme is different fromload of the MME when service data is transmitted by using the controlplane scheme, the MME may instruct, as required, the access networkdevice to bar and/or allow a service transmitted by using a transmissionscheme type, so that when the load of the MME is relatively heavy,access of a service transmitted by using a transmission scheme typecorresponding to heavier load is barred, but a service transmitted byusing a transmission scheme type corresponding to lighter load may stillbe received. This improves network resource utilization.

A data transmission attribute includes a transmission scheme type and/ora RAT type. The following embodiment is described by using an example inwhich the data transmission attribute is the RAT type. In this case, adata transmission attribute field is a RAT type field.

Referring to FIG. 8A and FIG. 8B, FIG. 8A and FIG. 8B are a flowchart ofa radio access control method according to an example embodiment of thepresent invention. This embodiment is described by using an example inwhich the method is applied to the radio access control system shown inFIG. 1 . The method includes the following steps.

Step 801: An MME sends an overload start message to an access networkdevice when load is greater than a preset condition, where the overloadstart message indicates a barred service type and a barred RAT typeand/or an allowed service type and an allowed RAT type to the accessnetwork device.

Two different implementations are available for the MME to send theoverload start message to the access network device to indicate thebarred service type and the barred RAT type and/or the allowed servicetype and the allowed RAT type. The overload start message includesdifferent content in different implementations.

In a first possible implementation, the overload start message includesa service type field and a RAT type field. The overload start messagehas a default action type. The action type is at least one of accessbarred and access allowed. The default action type of the overload startmessage may be preset.

In a second possible implementation, the overload start message includesan action type field, a service type field, and a RAT type field. Theaction type field indicates an action type of the overload startmessage, and the action type field includes at least one of accessbarred and access allowed.

An implementation used in this step is not limited in this embodiment.

The RAT type field indicates a radio access technology used by aterminal device. The RAT type field includes at least one of theWB-E-UTRAN and the NB-IoT.

Optionally, the RAT type field may further include 5G or another radioaccess technology. This is not limited in this embodiment.

In the two possible implementations, a service type indicated by theservice type field is the same as that in the embodiment shown in FIG.6A and FIG. 6B. For a possible form and content of the overload startmessage, refer to the overload start message illustrated in step 601 inFIG. 6A. Details are not described again in this embodiment.

Step 802: The access network device receives the overload start messagesent by the MME.

For a method for determining the action type and the service type of theoverload start message by the access network device, refer to step 602in the embodiment shown in FIG. 6A. Details are not described again inthis embodiment. In this embodiment, the access network devicedetermines the action type and the service type, and parses the RAT typefield to obtain a RAT type.

Step 803: The access network device generates access control informationbased on the overload start message, where the access controlinformation indicates the barred service type and the barred RAT typeand/or the allowed service type and the allowed RAT type to a terminaldevice.

An action type indicated by the access control information is the sameas the default action type that is of the overload start message andthat is determined by the access network device.

A service type indicated by the access control information is the sameas the service type obtained by the access network device by parsing theservice type field in the overload start message. A RAT type indicatedby the access control information is the same as the RAT type obtainedby the access network device by parsing the data transmission attributefield in the overload start message.

Two different implementations are available for the access networkdevice to indicate the barred service type and the barred RAT typeand/or the allowed service type and the allowed RAT type to the terminaldevice by using the generated access control information. The accesscontrol information includes different content in differentimplementations.

In a first possible implementation, the access control informationincludes a service type field and a RAT type field. The access controlinformation has a default action type. The action type is at least oneof access barred and access allowed.

In a second possible implementation, the access control informationincludes an action type field, a service type field, and a RAT typefield. The action type field indicates an action type of the accesscontrol information, and the action type field includes at least one ofaccess barred and access allowed.

An implementation used in this step is not limited in this embodiment.

A form of the access control information may be the same as the form ofthe overload start message. Details are not described again in thisembodiment.

Step 804: The access network device sends the access control informationto the terminal device.

For a method for sending the access control information to the terminaldevice by the access network device, refer to step 604 in the embodimentshown in FIG. 6A. Details are not described again in this embodiment.

Step 805: The terminal device receives the access control informationsent by the access network device.

For a method for determining the action type and the service type of theaccess control information by the terminal device, refer to step 605 inthe embodiment shown in FIG. 6A. Details are not described again in thisembodiment. In this embodiment, the terminal device determines theaction type and the service type, and parses the RAT type field toobtain a RAT type.

The action type is at least one of access barred and access allowed.When the action type is access allowed, the method includes thefollowing step 806:

Step 806: The terminal device sends an RRC connection request to theaccess network device when a service type of a current service meets theallowed service type and a RAT type corresponding to the current servicemeets the allowed RAT type.

The RAT type corresponding to the current service is a RAT type used bythe terminal device transmitting the current service for accessing theaccess network device.

The service type obtained by the terminal device by parsing the servicetype field in the access control information is an allowed service. TheRAT type obtained by parsing the RAT type field is the allowed RAT type.

When a service currently transmitted by the terminal device is anallowed service, and a used RAT type is the allowed RAT type, theterminal device sends the RRC connection request to the access networkdevice by using the RAT type.

Two different implementations are available when the action type isaccess barred.

In a first implementation, the access control information received bythe terminal device includes an access control factor and an accesscontrol time period. The terminal device determines, based on the accesscontrol factor and the access control time period, whether to send anRRC connection request to the access network device. Meanings of theaccess control factor and the access control time period in thisembodiment are the same as meanings of the access control factor and theaccess control time period in the foregoing embodiment. Details are notdescribed again in this embodiment.

In a second implementation, the access control information received bythe terminal device includes an access barring class. The terminaldevice determines, based on the access barring class, whether to send anRRC connection request to the access network device.

In this embodiment, if the first implementation is used as an examplefor description, the method further includes the following step 807 tostep 810.

Step 807: Generate a random number when a service type of a currentservice meets the barred service type and a RAT type corresponding tothe current service meets the barred RAT type.

Step 808: The terminal device determines whether the random number isless than an access control factor.

Step 809: When the random number is less than the access control factor,the terminal device determines to send an RRC connection request to theaccess network device.

Step 810: When the random number is greater than or equal to the accesscontrol factor, set a timer based on an access control time period, andwhen the timer expires, re-execute the step of generating a randomnumber.

For a specific implementation in which the terminal device uses thefirst implementation to determine whether to send the RRC connectionrequest to the access network device, refer to step 607 to step 610 inthe embodiment shown in FIG. 6B. Details are not described again in thisembodiment.

It should be noted that one piece of access control information mayindicate a plurality of action types, and the action types may includeboth access allowed and access barred. Implementations of the actiontype of access allowed and the action type of access barred are the sameas those in the foregoing method. Details are not described again inthis embodiment.

Another optional embodiment based on the foregoing embodiment isdescribed by using an example in which the action type of the accesscontrol information received by the terminal device is access barred,and the second implementation is used to determine whether to send theRRC connection request to the access network device. In this case, theaccess control information received by the terminal device furtherincludes the access barring class, and step 807 to step 810 may bealternatively implemented as any one of the following steps, as shown inFIG. 9 .

Step 901: When a service type of a current service meets the barredservice type and a RAT type corresponding to the current service meetsthe barred RAT type, detect whether an access class of the terminaldevice is equal to an access barring class; and if the access class ofthe terminal device is not equal to the access barring class, theterminal device determines to send an RRC connection request to theaccess network device.

Alternatively, another alternative implementation solution of step 901is illustrated in step 902.

Step 902: When a service type of a current service meets the barredservice type and a RAT type corresponding to the current service meetsthe barred RAT type, detect whether an access class of the terminaldevice is greater than an access barring class; and if the access classof the terminal device is less than the access barring class, determineto send an RRC connection request to the access network device.

Alternatively, another alternative implementation solution of step 901is illustrated in step 903.

Step 903: When a service type of a current service meets the barredservice type and a RAT type corresponding to the current service meetsthe barred RAT type, detect whether an access class of the terminaldevice is less than an access barring class; and if the access class ofthe terminal device is greater than the access barring class, determineto send an RRC connection request to the access network device.

In this embodiment, for implementations of step 901 to step 903, referto step 701 to step 703 in the embodiment shown in FIG. 7 . Details arenot described again in this embodiment. The terminal device executes anyone of step 901 to step 903. A specific used step is not limited in thisembodiment.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME whose load isrelatively heavy instructs to bar and/or allow access of some servicesmeeting the data transmission attribute in a type of service, instead ofall services in this type of service. This resolves a problem of low MMEresource utilization caused because the MME whose load is relativelyheavy instructs the access network device to bar access of all servicesof a type, and achieves the following effect: The access network devicemay bar and/or allow, based on the instruction of the MME, only accessof a service that meets both the service type and the data transmissionattribute, and service capabilities are provided for as many servicetypes as possible without significantly increasing the load of the MME,thereby improving network resource utilization.

According to the radio access control method provided in this embodimentof this disclosure, the MME indicates the barred service type and thebarred RAT type and/or the allowed service type and the allowed RAT typeto the access network device. In this way, the MME may instruct theaccess network device to receive only a service transmitted by aterminal device that gets access by using a RAT type. A first-typeterminal device that gets access by using the WB-E-UTRAN is usually aterminal device used by a user, and a second-type terminal device thatgets access by using the NB-IoT is usually a smart instrument or a smartmeter. Therefore, when the load of the MME is relatively heavy, the MMEmay instruct, as required, to bar and/or allow a service transmitted bya terminal device that gets access by using a RAT type, so that only aservice transmitted by a type of terminal device may be received asrequired when the load of the MME is relatively heavy. This improvesnetwork service quality.

A data transmission attribute includes a transmission scheme type and/ora RAT type. The following embodiment is described by using an example inwhich the data transmission attribute includes the transmission schemetype and the RAT type.

Referring to FIG. 10A and FIG. 10B, FIG. 10A and FIG. 10B are aflowchart of a radio access control method according to an exampleembodiment of the present invention. This embodiment is described byusing an example in which the method is applied to the radio accesscontrol system shown in FIG. 1 . The method includes the followingsteps.

Step 1001: An MME sends an overload start message to an access networkdevice when load is greater than a preset condition, where the overloadstart message indicates a barred service type and a barred datatransmission attribute and/or an allowed service type and an alloweddata transmission attribute to the access network device.

In this embodiment, the data transmission attribute includes atransmission scheme type and a RAT type. The transmission scheme typeindicates a transmission scheme used by a terminal device fortransmitting service data. The RAT type indicates a radio accesstechnology used by the terminal device.

Two different implementations are available for the MME to send theoverload start message to the access network device to indicate thebarred service type and the barred data transmission attribute and/orthe allowed service type and the allowed data transmission attribute.The overload start message includes different content in differentimplementations.

In a first possible implementation, the overload start message includesa service type field and a data transmission attribute field. Theoverload start message has a default action type. The action type is atleast one of access barred and access allowed. The default action typeof the overload start message may be preset.

In a second possible implementation, the overload start message includesan action type field, a service type field, and a data transmissionattribute field. The action type field indicates an action type of theoverload start message, and the action type field includes at least oneof access barred and access allowed.

An implementation used in this step is not limited in this embodiment.

In the two possible implementations, a service type indicated by theservice type field is the same as the service type illustrated in theforegoing embodiment. The data transmission attribute field includes atransmission scheme type field and a RAT type field. The transmissionscheme type field is the same as that in the embodiment shown in FIG. 6Aand FIG. 6B. The RAT type field is the same as that in the embodimentshown in FIG. 8A and FIG. 8B. Details are not described again in thisembodiment.

For example, if the default action type of the overload start messagesent by the MME to the access network device is access allowed, and theoverload start message is (mo-Data, WB-E-UTRAN, UP), it indicates thatan allowed service is a mo-Data service transmitted by using a UP schemeby a terminal device that gets access by using the WB-E-UTRAN.Alternatively, if the overload start message may be (barred, mo-Data,NB-IoT, CP), it indicates that a barred service is a mo-Data servicetransmitted by using a CP scheme by a terminal device that gets accessby using the NB-IoT. A form and content of the overload start messageare not limited in this embodiment.

Step 1002: The access network device receives the overload start messagesent by the MME.

For a method for determining the action type and the service type of theoverload start message by the access network device, refer to step 602in the embodiment shown in FIG. 6A. Details are not described again inthis embodiment. In this embodiment, the access network devicedetermines the action type and the service type, and parses the datatransmission type field to obtain the transmission scheme type and theRAT type.

Step 1003: The access network device generates access controlinformation based on the overload start message, where the accesscontrol information indicates the barred service type and the barreddata transmission attribute and/or the allowed service type and theallowed data transmission attribute to a terminal device.

An action type indicated by the access control information is the sameas the default action type that is of the overload start message andthat is determined by the access network device.

A service type indicated by the access control information is the sameas the service type obtained by the access network device by parsing theservice type field in the overload start message. A data transmissionattribute indicated by the access control information is the same as thedata transmission attribute obtained by the access network device byparsing the data transmission attribute field in the overload startmessage. Specifically, a transmission scheme type indicated by theaccess control information is the same as the transmission scheme typein the overload start message, and a RAT type indicated by the accesscontrol information is the same as the RAT type in the overload startmessage.

Two different implementations are available for the access networkdevice to indicate the barred service type and the barred datatransmission attribute and/or the allowed service type and the alloweddata transmission attribute to the terminal device by using thegenerated access control information. The access control informationincludes different content in different implementations.

In a first possible implementation, the access control informationincludes a service type field and a data transmission attribute field.The access control information has a default action type. The actiontype is at least one of access barred and access allowed.

In a second possible implementation, the access control informationincludes an action type field, a service type field, and a datatransmission attribute field. The action type field indicates an actiontype of the access control information, and the action type fieldincludes at least one of access barred and access allowed.

An implementation used in this step is not limited in this embodiment.

A form of the access control information may be the same as the form ofthe overload start message. Details are not described again in thisembodiment.

Step 1004: The access network device sends the access controlinformation to the terminal device.

A method for sending the access control information by the accessnetwork device to the terminal device is the same as that in theforegoing embodiment. Details are not described again in thisembodiment.

Step 1005: The terminal device receives the access control informationsent by the access network device.

For a method for determining the action type and the service type of theaccess control information by the terminal device, refer to step 605 inthe embodiment shown in FIG. 6A. Details are not described again in thisembodiment. In this embodiment, the terminal device determines theaction type and the service type, and parses the data transmissionattribute field to obtain the transmission scheme type and the RAT type.

The action type is at least one of access barred and access allowed.When the action type is access allowed, the method includes thefollowing step 1006:

Step 1006: The terminal device sends an RRC connection request to theaccess network device when a service type of a current service meets theallowed service type and a data transmission attribute corresponding tothe current service meets the allowed data transmission attribute.

The data transmission attribute corresponding to the current service isa RAT type used by the terminal transmitting the current service foraccessing the access network device, and a transmission scheme type usedby the terminal device for transmitting the current service.

The service type obtained by the terminal device by parsing the servicetype field in the access control information is an allowed service. Thetransmission scheme type and the RAT type that are obtained by parsingthe data transmission attribute field is an allowed transmission schemetype and an allowed RAT type.

When a service currently transmitted by the terminal device is anallowed service, a used transmission scheme type is the allowedtransmission scheme type, and a used RAT type is the allowed RAT type,the terminal device sends the RRC connection request to the accessnetwork device by using the RAT type.

Two different implementations are available when the action type isaccess barred.

In a first implementation, the access control information received bythe terminal device includes an access control factor and an accesscontrol time period. The terminal device determines, based on the accesscontrol factor and the access control time period, whether to send anRRC connection request to the access network device. Meanings of theaccess control factor and the access control time period in thisembodiment are the same as meanings of the access control factor and theaccess control time period in the foregoing embodiment. Details are notdescribed again in this embodiment.

In a second implementation, the access control information received bythe terminal device includes an access barring class. The terminaldevice determines, based on the access barring class, whether to send anRRC connection request to the access network device.

In this embodiment, if the first implementation is used as an examplefor description, the method further includes the following step 1007 tostep 1010.

Step 1007: Generate a random number when a service type of a currentservice meets the barred service type and a data transmission attributecorresponding to the current service meets the barred data transmissionattribute.

Step 1008: The terminal device determines whether the random number isless than an access control factor.

Step 1009: When the random number is less than the access controlfactor, the terminal device determines to send an RRC connection requestto the access network device.

Step 1010: When the random number is greater than or equal to the accesscontrol factor, set a timer based on an access control time period, andwhen the timer expires, re-execute the step of generating a randomnumber.

For a specific implementation in which the terminal device uses thefirst implementation to determine whether to send the RRC connectionrequest to the access network device, refer to step 607 to step 610 inthe embodiment shown in FIG. 6B. Details are not described again in thisembodiment.

It should be noted that one piece of access control information mayindicate a plurality of action types, and the action types may includeboth access allowed and access barred. Implementations of the actiontype of access allowed and the action type of access barred are the sameas those in the foregoing method. Details are not described again inthis embodiment.

Another optional embodiment based on the foregoing embodiment isdescribed by using an example in which the action type of the accesscontrol information received by the terminal device is access barred,and the second implementation is used to determine whether to send theRRC connection request to the access network device. In this case, theaccess control information received by the terminal device furtherincludes the access barring class, and step 1007 to step 1010 may bealternatively implemented as any one of the following steps, as shown inFIG. 11 .

Step 1101: When a service type of a current service meets the barredservice type and a data transmission attribute corresponding to thecurrent service meets the barred data transmission attribute, detectwhether an access class of the terminal device is equal to an accessbarring class; and if the access class of the terminal device is notequal to the access barring class, the terminal device determines tosend an RRC connection request to the access network device.

Step 1102: When a service type of a current service meets the barredservice type and a data transmission attribute corresponding to thecurrent service meets the barred data transmission attribute, detectwhether an access class of the terminal device is greater than an accessbarring class; and if the access class of the terminal device is lessthan the access barring class, determine to send an RRC connectionrequest to the access network device.

Step 1103: When a service type of a current service meets the barredservice type and a data transmission attribute corresponding to thecurrent service meets the barred data transmission attribute, detectwhether an access class of the terminal device is less than an accessbarring class; and if the access class of the terminal device is greaterthan the access barring class, determine to send an RRC connectionrequest to the access network device.

In this embodiment, for implementations of step 1101 to step 1103, referto step 701 to step 703 in the embodiment shown in FIG. 7 . Details arenot described again in this embodiment. The terminal device executes anyone of step 1101 to step 1103. A specific used step is not limited inthis embodiment.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME whose load isrelatively heavy instructs to bar and/or allow access of some servicesmeeting the data transmission attribute in a type of service, instead ofall services in this type of service. This resolves a problem of low MMEresource utilization caused because the MME whose load is relativelyheavy instructs the access network device to bar access of all servicesof a type, and achieves the following effect: The access network devicemay bar and/or allow, based on the instruction of the MME, only accessof a service that meets both the service type and the data transmissionattribute, and service capabilities are provided for as many servicetypes as possible without significantly increasing the load of the MME,thereby improving network resource utilization.

According to the radio access control method provided in thisembodiment, the MME indicates the barred service type and the barreddata transmission attribute and/or the allowed service type and theallowed data transmission attribute to the access network device. Thedata transmission attribute includes the transmission scheme type andthe RAT type. In this way, the MME may instruct the access networkdevice to bar and/or allow a service transmitted by using a transmissionscheme type by a terminal device that gets access by using a RAT type.When the load of the MME is relatively heavy, a service that iscorresponding to lighter load and that is transmitted by a type ofterminal device may still be allowed. This improves network resourceutilization, and improves network service quality.

Referring to FIG. 12A, FIG. 12A is a flowchart of a radio access controlmethod according to another example embodiment of the present invention.This embodiment is described by using an example in which the method isapplied to the radio access control system shown in FIG. 1 . The methodincludes the following steps.

Step 1201: An MME sends an overload start message to an access networkdevice when load is greater than a preset condition, where the overloadstart message indicates a barred service type and a barred datatransmission attribute and/or an allowed service type and an alloweddata transmission attribute to the access network device.

Step 1202: The access network device receives the overload start messagesent by the MME.

A method for determining the barred service type and the barred datatransmission attribute and/or the allowed service type and the alloweddata transmission attribute by the access network device based on theoverload start message is the same as that in the foregoing embodiment.Details are not described again in this embodiment.

Step 1203: A terminal device sends an RRC connection request message tothe access network device, where the RRC connection request has acorresponding service type and a corresponding data transmissionattribute.

The RRC connection request is triggered by a service transmitted by theterminal device. The service type and the data transmission attributethat are corresponding to the RRC connection request are a type of theservice that triggers the RRC connection request and a data transmissionattribute used when the terminal device transmits the service.

For example, if the RRC connection request is triggered when theterminal device uses a CP scheme to transmit a mo-Data service, theservice type corresponding to the RRC connection request is the mo-Dataservice, and the data transmission attribute corresponding to the RRCconnection request is the CP scheme.

Optionally, the RRC connection request message further includes aservice type field and a data transmission attribute field.

The service type field indicates a service type. The data transmissionattribute field indicates a data transmission attribute. Content of theservice type field and the data transmission attribute field is the sameas that in the foregoing example embodiment. Details are not describedagain in this embodiment.

Step 1204: The access network device receives the RRC connection requestmessage sent by the terminal device.

The access network device parses the RRC connection request message todetermine the service type and the data transmission attribute that arecorresponding to the RRC connection request.

Step 1205: The access network device sends an RRC connection setupmessage or an RRC connection reject message to the terminal device basedon whether the service type and the data transmission attribute that arecorresponding to the RRC connection request belong to the barred servicetype and the barred data transmission attribute and/or the allowedservice type and the allowed data transmission attribute.

When the service type and the data transmission attribute that arecorresponding to the RRC connection request are the allowed service typeand the allowed data transmission attribute, the RRC connection setupmessage is sent to the terminal device, and an RRC connection isestablished with the terminal device.

The RRC connection reject message is sent to the terminal device whenthe service type and the data transmission attribute that arecorresponding to the RRC connection request are the barred service typeand the barred data transmission attribute.

Optionally, two different implementations are further included when theservice type and the data transmission attribute that are correspondingto the RRC connection request are the barred service type and the barreddata transmission attribute.

In a first possible implementation, when the service type and the datatransmission attribute that are corresponding to the RRC connectionrequest are the barred service type and the barred data transmissionattribute, the access network device generates a random number, anddetermines whether the random number is less than an access controlfactor. The access network device sends an RRC connection requestmessage to the terminal device when the random number is less than theaccess control factor. The access network device sends an RRC connectionreject message to the terminal device when the random number is not lessthan the access control factor. For a meaning and a specificimplementation of the access control factor, refer to the foregoingembodiment. Details are not described again in this embodiment.

In a second possible implementation, the RRC connection request messagefurther includes an access class of the terminal device.

When the service type and the data transmission attribute that arecorresponding to the RRC connection request are the barred service typeand the barred data transmission attribute, the access network devicedetermines whether the access class of the terminal device is equal toan access barring class. If the access class of the terminal device isnot equal to the access barring class, the access network device sendsan RRC connection setup message to the terminal device. If the accessclass of the terminal device is equal to the access barring class, theaccess network device sends an RRC connection reject message to theterminal device. The method may be alternatively implemented asdetecting whether the access class of the terminal device is greaterthan or less than the access barring class. A specific implementation issimilar to that in the foregoing embodiment. Details are not describedagain in this embodiment.

Step 1206: The terminal device receives the RRC connection setup messageor the RRC connection reject message sent by the access network device.

In the embodiment shown in FIG. 12A, the service type and the datatransmission attribute that are corresponding to the RRC connectionrequest are sent together with the RRC connection request message. Inanother optional embodiment, the terminal device may alternatively sendonly the service type corresponding to the RRC connection requesttogether with the RRC connection message request, and send the datatransmission attribute corresponding to the RRC connection requestbefore sending the RRC connection message request. In this case, step1201 and step 1204 may be alternatively implemented as the followingsteps, as shown in FIG. 12B.

Step 1210: An MME sends an overload start message to an access networkdevice when load is greater than a preset condition, where the overloadstart message indicates a barred service type and a barred datatransmission attribute and/or an allowed service type and an alloweddata transmission attribute to the access network device.

Step 1211: The access network device receives the overload start messagesent by the MME.

Step 1212: A terminal device sends a data transmission attributecorresponding to an RRC connection request to the access network device.

Step 1213: The access network receives the data transmission attributethat is corresponding to the RRC connection request and that is sent bythe terminal device.

Optionally, the access network device sends a correspondence between arandom access preamble (Random Access Preamble) and a data transmissionattribute to the terminal device in advance. The terminal deviceselects, based on the data transmission attribute corresponding to theRRC connection request, a preamble corresponding to the datatransmission attribute to send a random access request to the accessnetwork device. The access network device determines, based on thepreamble used by the random access request sent by the terminal device,the data transmission attribute corresponding to the RRC connectionrequest.

For example, when the data transmission attribute includes atransmission scheme type: a CP scheme or a UP scheme, the access networkdevice pre-notifies the terminal device that a preamble A iscorresponding to the CP scheme and a preamble B is corresponding to theUP scheme. If a service that triggers the terminal device to initiatethe RRC connection request uses the CP scheme, the terminal deviceselects the preamble A to initiate a random access request to the accessnetwork device. The access network device receives the random accessrequest, and determines, based on the preamble A used by the randomaccess request, that the data transmission attribute corresponding tothe RRC connection request of the terminal device is the CP scheme.

For another example, when the data transmission attribute includes aradio access technology: the WB-E-UTRAN or the NB-IoT, the accessnetwork device pre-notifies the terminal device that a preamble C iscorresponding to the WB-E-UTRAN and a preamble D is corresponding to theNB-IoT. If a service that triggers the terminal device to initiate theRRC connection request uses the NB-IoT, the terminal device selects thepreamble D to initiate a random access request to the access networkdevice. The access network device receives the random access request,and determines, based on the preamble D used by the random accessrequest, that the data transmission attribute corresponding to the RRCconnection request of the terminal device is the NB-IoT.

Step 1214: The terminal device sends the RRC connection request messageto the access network device, where the RRC connection request has acorresponding service type and a corresponding data transmissionattribute.

The RRC connection request message further includes a service typefield.

The service type field indicates a service type. Content of the servicetype field is the same as that in the foregoing example embodiment.Details are not described again in this embodiment.

Step 1215: The access network device receives the RRC connection requestmessage sent by the terminal device.

In view of the above, according to the radio access control methodprovided in this embodiment of this disclosure, the MME whose load isrelatively heavy instructs to bar and/or allow access of some servicesmeeting the data transmission attribute in a type of service, instead ofall services in this type of service. This resolves a problem of low MMEresource utilization caused because the MME whose load is relativelyheavy instructs the access network device to bar access of all servicesof a type, and achieves the following effect: The access network devicemay bar and/or allow, based on the instruction of the MME, only accessof a service that meets both the service type and the data transmissionattribute, and service capabilities are provided for as many servicetypes as possible without significantly increasing the load of the MME,thereby improving network resource utilization.

The following are apparatus embodiments of the present invention, andthe apparatus embodiments may be used to execute the method embodimentsof the present invention. For details not disclosed in the apparatusembodiments of the present invention, refer to the method embodiments ofthe present invention.

Referring to FIG. 13A, FIG. 13A is a structural block diagram of a radioaccess control apparatus according to an embodiment of the presentinvention. The radio access control apparatus may be implemented as apart or all of a terminal device by using software, hardware, or acombination of the software and the hardware. The radio access controlapparatus may include:

a receiving unit 1310, configured to receive access control informationsent by an access network device, where the access control informationindicates a barred service type and a barred data transmission attributeand/or an allowed service type and an allowed data transmissionattribute to the terminal device, the data transmission attributeincludes a transmission scheme type and/or a RAT type, the transmissionscheme type indicates a transmission scheme used by the terminal devicefor transmitting service data, and the RAT type indicates a radio accesstechnology used by the terminal device; and

a processing unit 1320, configured to determine, based on the servicetype and the data transmission attribute, whether to send an RRCconnection request to the access network device.

For related details, refer to the foregoing method embodiment.

In another optional embodiment, the access control information includesan access control factor and an access control time period.

The processing unit 1320 is further configured to generate a randomnumber when a service type of a current service meets the barred servicetype and a data transmission attribute corresponding to the currentservice meets the barred data transmission attribute.

The processing unit 1320 is further configured to determine whether therandom number is less than the access control factor included in theaccess control information.

The processing unit 1320 is further configured to: when the randomnumber is less than the access control factor, determine to send the RRCconnection request to the access network device by using acommunications unit.

The processing unit 1320 is further configured to: when the randomnumber is greater than or equal to the access control factor, set atimer based on the access control time period included in the accesscontrol information, and when the timer expires, re-execute the step ofgenerating a random number.

For related details, refer to the foregoing method embodiment.

In another optional embodiment, the radio access control apparatus shownin FIG. 13A further includes a sending unit 1330, and the access controlinformation includes an access barring class.

The processing unit 1320 is further configured to: when a service typeof a current service meets the barred service type and a datatransmission attribute corresponding to the current service meets thebarred data transmission attribute, detect whether an access class ofthe terminal device is equal to the access barring class included in theaccess control information; and if the access class of the terminaldevice is not equal to the access barring class, determine to send theRRC connection request to the access network device by using the sendingunit 1330; or

the processing unit 1320 is further configured to: when a service typeof a current service meets the barred service type and a datatransmission attribute corresponding to the current service meets thebarred data transmission attribute, detect whether an access class ofthe terminal device is greater than the access barring class included inthe access control information; and if the access class of the terminaldevice is less than the access barring class, determine to send the RRCconnection request to the access network device by using the sendingunit 1330; or

the processing unit 1320 is further configured to: when a service typeof a current service meets the barred service type and a datatransmission attribute corresponding to the current service meets thebarred data transmission attribute, detect whether an access class ofthe terminal device is less than the access barring class included inthe access control information; and if the access class of the terminaldevice is greater than the access barring class, determine to send theRRC connection request to the access network device by using the sendingunit 1330.

For related details, refer to the foregoing method embodiment.

In another optional embodiment, the radio access control apparatus shownin FIG. 13A further includes a sending unit 1330. The determining unit1320 is further configured to: when a service type of a current servicemeets the barred service type and a data transmission attributecorresponding to the current service meets the allowed data transmissionattribute, send the RRC connection request to the access network deviceby using the sending unit 1330.

For related details, refer to the foregoing method embodiment.

In another optional embodiment, as shown in FIG. 13B, the radio accesscontrol apparatus shown in FIG. 13A further includes a sending unit1330.

The sending unit 1330 is further configured to send the RRC connectionrequest message to the access network device, where the RRC connectionrequest has a corresponding service type and a corresponding datatransmission attribute.

The receiving unit 1310 is further configured to receive an RRCconnection setup message or an RRC connection reject message sent by theaccess network device, where the RRC connection setup message or the RRCconnection reject message is sent by the access network device based onwhether the service type and the data transmission attribute that arecorresponding to the RRC connection request belong to the barred servicetype and the barred data transmission attribute and/or the allowedservice type and the allowed data transmission attribute.

The receiving unit 1310 is further configured to send the datatransmission attribute corresponding to the RRC connection request tothe access network device.

It should be noted that the radio access control apparatus shown in FIG.13A and/or the radio access control apparatus shown in FIG. 13B are/isconfigured to implement the radio access control method. The terminaldevice may receive information by using the receiving unit, the terminaldevice may send information by using the sending unit, and the terminaldevice may execute, by using the processing unit, a step of determiningwhether to send and/or receive information.

An entity apparatus corresponding to the receiving unit is a receiver ofthe terminal device, an entity apparatus corresponding to the sendingunit is a transmitter of the terminal device, and an entity apparatuscorresponding to the processing unit is a processor of the terminaldevice.

Referring to FIG. 14 , FIG. 14 is a structural block diagram of a radioaccess control apparatus according to an embodiment of the presentinvention. The radio access control apparatus may be implemented as apart or all of an access network device by using software, hardware, ora combination of the software and the hardware. The radio access controlapparatus may include:

a receiving unit 1410, configured to receive an overload start messagesent by a mobility management entity MME, where the overload startmessage indicates a barred service type and a barred data transmissionattribute and/or an allowed service type and an allowed datatransmission attribute to the access network device, the datatransmission attribute includes a transmission scheme type and/or a RATtype, the transmission scheme type indicates a transmission scheme usedby the terminal device for transmitting service data, and the RAT typeindicates a radio access technology used by the terminal device;

a processing unit 1420, configured to generate access controlinformation based on the overload start message received by thereceiving unit 1410, where the access control information indicates thebarred service type and the barred data transmission attribute and/orthe allowed service type and the allowed data transmission attribute tothe terminal device; and

a sending unit 1430, configured to send the access control informationto the terminal device.

For related details, refer to the foregoing method embodiment.

In an optional embodiment, the receiving unit 1410 is further configuredto receive an RRC connection request message sent by the terminaldevice, where the RRC connection request has a corresponding servicetype and a corresponding data transmission attribute.

The sending unit 1430 is further configured to send an RRC connectionsetup message or an RRC connection reject message to the terminal devicebased on whether the service type and the data transmission attributethat are corresponding to the RRC connection request belong to thebarred service type and the barred data transmission attribute and/orthe allowed service type and the allowed data transmission attribute.

The receiving unit 1410 is further configured to receive the datatransmission attribute that is corresponding to the RRC connectionrequest and that is sent by the terminal device.

It should be noted that the radio access control apparatus shown in FIG.14 is configured to implement the radio access control method. Theaccess network device may receive information by using the receivingunit, the access network device can send information by using thesending unit, and the access network device may execute, by using theprocessing unit, a step of processing information.

An entity apparatus corresponding to the receiving unit is a receiver ofthe access network device, an entity apparatus corresponding to thesending unit is a transmitter of the access network device, and anentity apparatus corresponding to the processing unit is a processor ofthe access network device.

Referring to FIG. 15 , FIG. 15 is a structural block diagram of a radioaccess control apparatus according to an embodiment of the presentinvention. The radio access control apparatus may be implemented as apart or all of an MME by using software, hardware, or a combination ofthe software and the hardware. The radio access control apparatus mayinclude:

a sending unit 1510, configured to send an overload start message to anaccess network device when load is greater than a preset condition,where the overload start message indicates a barred service type and abarred data transmission attribute and/or an allowed service type and anallowed data transmission attribute to the access network device, thedata transmission attribute includes a transmission scheme type and/or aRAT type, the transmission scheme type indicates a transmission schemeused by a terminal device for transmitting service data, and the RATtype indicates a radio access technology used by the terminal device.

For related details, refer to the foregoing method embodiment.

It should be noted that the radio access control apparatus shown in FIG.15 is configured to implement the radio access control method. The MMEmay send information by using the sending unit. The radio access controlapparatus shown in FIG. 15 may further include a receiving unit and aprocessing unit. The MME may receive information by using the receivingunit, and the MME may execute, by using the processing unit, a step ofprocessing information.

An entity apparatus corresponding to the receiving unit is a receiver ofthe MME, an entity apparatus corresponding to the sending unit is atransmitter of the MME, and an entity apparatus corresponding to theprocessing unit is a processor of the MME.

It should be noted that, when the radio access control apparatusprovided in the embodiment controls radio access, division of thefunction modules are merely used as an example for description. Inactual application, the functions may be allocated to different functionmodules and implemented as required. In other words, an internalstructure of the apparatus is divided into different function modules toimplement all or some functions described above. In addition, the radioaccess control apparatus provided in the embodiment pertains to a sameconcept as the method embodiment of the radio access control method. Fora specific implementation process of the radio access control apparatus,refer to the method embodiment. Details are not described herein again.

It should be understood that the singular form “one” (“a”, “an”, or“the”) used in this specification is intended to further include aplural form unless the context clearly supports an exception. It shouldbe further understood that “and/or” used in this specification means toinclude any or all possible combinations of one or more associatedlisted items.

The sequence numbers of the embodiments of the present invention aremerely for illustrative purposes, and are not intended to indicatepriorities of the embodiments.

A person of ordinary skill in the art may understand that all or some ofthe steps of the embodiments may be implemented by hardware or a programinstructing related hardware. The program may be stored in acomputer-readable storage medium. The storage medium may include: aread-only memory, a magnetic disk, an optical disc, or the like.

The foregoing descriptions are merely example embodiments of the presentinvention, but are not intended to limit the present invention. Anymodification, equivalent replacement, and improvement made withoutdeparting from the spirit and principle of the present invention shallfall within the protection scope of the present invention.

The invention claimed is:
 1. A radio access control method, the methodcomprising: sending a first radio resource control (RRC) connectionrequest message to an access network device, the first RRC connectionrequest message having a service type and a data transmission attribute,the data transmission attribute comprising at least one of atransmission scheme type or a Radio Access Technology (RAT) type, thetransmission scheme type indicating a transmission scheme used by aterminal device for transmitting service data used by the terminaldevice, and the RAT type indicating a radio access technology used bythe terminal device; receiving access control information from theaccess network device, the access control information indicating abarred service type and a barred data transmission attribute, whereinthe service type belongs to the barred service type, and the datatransmission attribute belongs to the barred data transmissionattribute; and determining based on the barred service type and thebarred data transmission attribute, whether to send a second RRCconnection request message to the access network device.
 2. The methodaccording to claim 1, wherein: the access control information comprisesan action type field, a service type field, and a data transmissionattribute field, the action type field comprising an access barredaction type, and the data transmission attribute field comprising acontrol plane scheme.
 3. The method according to claim 2, wherein: thedata transmission attribute field comprises the RAT type, and the datatransmission attribute field comprises Narrow Band Internet of Things(NB-IoT).
 4. The method according to claim 2, wherein: the service typefield comprises at least one of a mobile originated data (mo-Data)service or a delay tolerant service (delayTolerantAccess).
 5. The methodaccording to claim 1, wherein: the service type is a type that triggersthe RRC connection request, and the data transmission attribute is anattribute used when the terminal device transmits the service.
 6. Themethod according to claim 1, wherein: the access control information isgenerated based on an overload start message, the overload start messageindicating the barred service type and the barred data transmissionattribute.
 7. A radio access control method, the method comprising:receiving, by an access network device, an overload start message from amobility management entity, the overload start message indicating abarred service type and a barred data transmission attribute;generating, by the access network device, access control informationbased on the overload start message, the access control informationindicating the barred service type and the barred data transmissionattribute; receiving, by the access network device, a radio resourcecontrol (RRC) connection request message from a terminal device, whereinthe RRC connection request message includes a service type and a datatransmission attribute, the service type belongs to the barred servicetype and the data transmission attribute belongs to the barred datatransmission attribute, the data transmission attribute comprises atleast one of a transmission scheme type or a Radio Access Technology(RAT) type, the transmission scheme type indicates a transmission schemeused by the terminal device for transmitting service data, and the RATtype indicates a radio access technology used by the terminal device;and sending, by the access network device, the access controlinformation to the terminal device.
 8. The method according to claim 7,wherein: the overload start message comprises an action type field, aservice type field, and a data transmission attribute field, the actiontype field comprising an access barred action type, and the datatransmission attribute field comprising a control plane scheme.
 9. Themethod according to claim 8, wherein: the data transmission attributefield comprises the RAT type, and the data transmission attribute fieldcomprises Narrow Band Internet of Things (NB-IoT).
 10. The methodaccording to claim 8, wherein: the service type field comprises at leastone of a mobile originated data (mo-Data) service or a delay tolerantservice (delayTolerantAccess).
 11. The method according to claim 7, themethod further comprising: parsing, by the access network device, theRRC connection request message to determine the service type and thedata transmission attribute.
 12. The method according to claim 7,wherein: the service type is a type that triggers the RRC connectionrequest message, and the data transmission attribute is an attributeused when the terminal device transmits the service.
 13. A radio accesscontrol apparatus, the apparatus comprising: a memory storinginstructions; and at least one processor in communication with thememory, the at least one processor configured, upon execution of theinstructions, to perform the following steps: send a first radioresource control (RRC) connection request message to an access networkdevice, the first RRC connection request having a service type and adata transmission attribute; receive access control information from theaccess network device, the access control information indicating abarred service type and a barred data transmission attribute, whereinthe service type belongs to the barred service type and the datatransmission attribute belongs to the barred data transmissionattribute, the data transmission attribute comprises at least one of atransmission scheme type or a Radio Access Technology (RAT) type, thetransmission scheme type indicates a transmission scheme used by aterminal device for transmitting service data, and the RAT typeindicates a radio access technology used by the terminal device; anddetermine, based on the barred service type and the barred datatransmission attribute, whether to send a second RRC connection requestmessage to the access network device.
 14. The apparatus according toclaim 13, wherein: the access control information comprises an actiontype field, a service type field, and a data transmission attributefield, the action type field comprising an access barred action type,and the data transmission attribute field comprising a control planescheme.
 15. The apparatus according to claim 14, wherein: the datatransmission attribute field comprises the RAT type, and the datatransmission attribute field comprises Narrow Band Internet of Things(NB-IoT).
 16. The apparatus according to claim 14, wherein: the servicetype field comprises at least one of a mobile originated data (mo-Data)service or a delay tolerant service (delayTolerantAccess).
 17. Theapparatus according to claim 13, wherein: the service type is a typethat triggers the RRC connection request, and the data transmissionattribute is an attribute used when the terminal device transmits theservice.
 18. A radio access control apparatus, the apparatus comprising:a memory storing instructions; and at least one processor incommunication with the memory, the at least one processor configured,upon execution of the instructions, to perform the following steps:receive an overload start message sent by a mobility management entity,the overload start message having a barred service type and a barreddata transmission attribute; generate access control information basedon the overload start message, the access control information indicatingthe barred service type and the barred data transmission attribute;receive a radio resource control (RRC) connection request message from aterminal device, the RRC connection request message including a servicetype and a data transmission attribute; wherein the service type belongsto the barred service type and the data transmission attribute belongsto the barred data transmission attribute, the data transmissionattribute comprises at least one of a transmission scheme type or aRadio Access Technology (RAT) type, the transmission scheme typeindicates a transmission scheme used by the terminal device fortransmitting service data, and the RAT type indicates a radio accesstechnology used by the terminal device; and send the access controlinformation to the terminal device.
 19. The apparatus according to claim18, wherein: the overload start message comprises an action type field,a service type field, and a data transmission attribute field, theaction type field comprising an access barred action type, and the datatransmission attribute field comprising a control plane scheme.
 20. Theapparatus according to claim 18, wherein: the service type fieldcomprises at least one of a mobile originated data (mo-Data) service ora delay tolerant service (delayTolerantAccess).
 21. A radio accesscontrol method, the method comprising: sending, by a mobility managemententity, an overload start message to an access network device, theoverload start message indicating a barred service type and a barreddata transmission attribute; receiving, by the access network device,the overload start message from the mobility management entity;generating, by the access network device, access control informationbased on the overload start message, the access control informationindicating the barred service type and the barred data transmissionattribute; receiving, by the access network device, a radio resourcecontrol (RRC) connection request message from a terminal device, whereinthe RRC connection request message includes a service type and a datatransmission attribute, the service type belongs to the barred servicetype and the data transmission attribute belongs to the barred datatransmission attribute, the data transmission attribute comprises atleast one of a transmission scheme type or a Radio Access Technology(RAT) type, the transmission scheme type indicates a transmission schemeused by the terminal device for transmitting service data, and the RATtype indicates a radio access technology used by the terminal device;and sending, by the access network device, the access controlinformation to the terminal device.
 22. The method according to claim21, wherein: the access control information comprises an action typefield, a service type field, and a data transmission attribute field,the action type field comprising an access barred action type, and thedata transmission attribute field comprising a control plane scheme. 23.The method according to claim 22, wherein: the data transmissionattribute field comprises the RAT type, and the data transmissionattribute field comprises Narrow Band Internet of Things (NB-IoT). 24.The method according to claim 22, wherein: the service type fieldcomprises at least one of a mobile originated data (mo-Data) service ora delay tolerant service (delayTolerantAccess).
 25. A system,comprising: a mobility management entity configured to send an overloadstart message to an access network device, the overload start messageindicating a barred service type and a barred data transmissionattribute; and the access network device configured to receive theoverload start message from the mobility management entity, generateaccess control information based on the overload start message, theaccess control information indicating the barred service type and thebarred data transmission attribute, receive a radio resource control(RRC) connection request message from a terminal device, wherein the RRCconnection request message includes a service type and a datatransmission attribute, the service type belongs to the barred servicetype and the data transmission attribute belongs to the barred datatransmission attribute, the data transmission attribute comprises atleast one of a transmission scheme type or a Radio Access Technology(RAT) type, the transmission scheme type indicates a transmission schemeused by the terminal device for transmitting service data, and the RATtype indicates a radio access technology used by the terminal device;and send the access control information to the terminal device.
 26. Thesystem according to claim 25, wherein: the access control informationcomprises an action type field, a service type field, and a datatransmission attribute field, the action type field comprising an accessbarred action type, and the data transmission attribute field comprisinga control plane scheme.
 27. The system according to claim 26, wherein:the data transmission attribute field comprises the RAT type, and thedata transmission attribute field comprises Narrow Band Internet ofThings (NB-IoT).
 28. The system according to claim 26, wherein: theservice type field comprises at least one of a mobile originated data(mo-Data) service or a delay tolerant service (delayTolerantAccess).